Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

Hi @adaosantos

Thanks a lot for the PR — I really appreciate the effort to organize the Fiber adapters into version-specific directories. The structure itself is clean and easy to follow 👍

Before merging, I’d like to align on a couple of forward-looking points.

First, there’s an ongoing discussion that Fiber v3 may include built-in OpenAPI support in the future
(ref: gofiber/fiber#3702).
Because of that, I want to be cautious about locking in long-term adapter structures that might become obsolete or require major refactoring once Fiber provides native OpenAPI functionality.

Second, I’d like to understand how this structure would evolve with oaswrap/spec versioning itself:

• How do you envision this layout working if/when the spec is released as v2?
• Would adapters be tied to the framework version only, the spec version, or a combination of both?
• Do you see a need for a formal versioning or compatibility mechanism going forward?

As a concrete reference, Datadog uses a combined framework-version approach for Fiber:
github.com/DataDog/dd-trace-go/contrib/gofiber/fiber.v2/v2
This makes the target framework version explicit at the import path level and helps avoid ambiguity when multiple major versions coexist. I’m curious how close (or different) your proposal is compared to this approach.